Application Specific Certificate Management

ABSTRACT

Application specific certificate deployment may be provided. An application may generate a security certificate comprising a public key and a first private key. The public key may be stored in a shared segment of a memory store, from where it may be retrieved and signed. The signed public key may be re-deployed and/or used to transmit securely encrypted resources.

BACKGROUND

Mobile device management often relies on utilizing existing mechanismsto add enhanced levels of security. For example, applications installedon a device may need to securely access enterprise resources and datadespite those applications not having established means for doing so. Avirtual private network (VPN) may sometimes be established to providesecure communication, but this process can be difficult and resourceintensive. Instead, existing channels of communication, such as may beprovided by an existing operating system on the device, may be leveragedwith other mechanisms, such as security certificates, to providelow-impact workarounds.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter. Neither is thisSummary intended to be used to limit the claimed subject matter's scope.

Application specific certificate deployment may be provided. Anapplication may generate a security certificate comprising a public keyand a first private key. The public key may be stored in a sharedsegment of a memory store, from where it may be retrieved and signed.The signed public key may be re-deployed and/or used to transmitsecurely encrypted resources.

It is to be understood that both the foregoing general description andthe following detailed description are examples and explanatory only,and should not be considered to restrict the disclosure's scope, asdescribed and claimed. Further, features and/or variations may beprovided in addition to those set forth herein. For example, embodimentsof the disclosure may be directed to various feature combinations andsub-combinations described in the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following diagrams. The drawings are not necessarily toscale. Instead, emphasis is placed upon clearly illustrating certainfeatures of the disclosure. Moreover, in the drawings, like referencenumerals designate corresponding parts throughout the several views. Inthe drawings:

FIG. 1 is a block diagram of an operating environment for providingdevice management;

FIG. 2 is a flow chart illustrating a method for providing applicationspecific certificate deployment.

FIG. 3 is a block diagram of a communication system providingapplication specific certificate deployment;

FIG. 4 is a schematic block diagram of a remote server and a clientdevice; and

FIG. 5 illustrates components of a virtual desktop infrastructure (VDI)system in which embodiments of the present disclosure may beimplemented.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of the disclosure may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe disclosure. Instead, the proper scope of the disclosure is definedby the appended claims.

Users of mobile devices often need to securely access resources and/ordata associated with an organization or enterprise. For example, a usermay wish to access a shared file folder hosted on a corporate intranet.In some cases, specific configurations, such as a VPN, may be needed toaccess these resources. In other cases, an application may be configuredto receive encrypted copies of the resources. The application stillneeds a way to ensure that the encryption mechanism is not compromised,however, when accessing these resources over a public or non-securechannel.

Some mobile device operating systems, such as Apple's iOS® 7, offerconfiguration channels that may be used for communicating directly withan application executing on the device. These channels, however, are notencrypted, and may be shared among multiple applications. In order toprovide an additional layer of security, the insecure communicationchannel may be used solely for communicating non-sensitive and/orencrypted information, such as the public key half of a securitycertificate or an encrypted private key. Since only the private key halfof the security certificate is considered sensitive, the public key maybe accessed by any other application or user without risk ofcompromising the secured data or resources.

The security certificate may be generated by the application wishing toaccess the resources, and the public key may be uploaded to the resourceprovider. The public key may then be used to encrypt the data. Theencrypted data can then be provided to the application over the sharedcommunication channel without risk of exposure, and the application mayuse the private key to decrypt the data.

In some embodiments, users, applications, and/or their devices may berequired to comply with management and/or security policies in order torequest resources, use certain features and/or to communicate with otherusers at all. For example, a device may need to comply with varioussecurity checks such as virus or malware scans, which applicationsand/or protocols may be used, operating system integrity (e.g., not be‘rooted’, ‘jailbroken’, or otherwise hacked), and/or user, group, and/ordevice authorizations. Management policies may restrict factors such astimes and/or locations in which such messages may be sent and/orreceived, a quota of resources that may be used by such messaging, whomay exchange messages with whom, and/or which user preferences and/orsettings may be enforceable.

Compliance with management and/or security policies may be required byan enterprise to prevent remediation actions from being taken. Forexample, a management policy may require that a device have a passcodeset, that a specific application be used for real-time communications,and that only users within the same user group may be messaged duringworking hours. Security policies may restrict encryption of the messagetraffic to an encryption key assigned by the enterprise, so thatmessages may be logged and/or audited, and may prohibit the sending offiles or images. Failure to comply with these policies may result, forexample, in restricting an input from being transmitted at all,overriding a user preference associated with the application (e.g.,using the enterprise encryption key instead of a personal key), and/orpreventing the establishment of a communication session between theusers at all.

The security policies may further comprise requirements to protect thecontent of the communication from unauthorized users. For example, anotification message on the receiving user's device may be prohibitedfrom displaying any and/or all of the contents of the communicationuntil an authorization, such as a passcode or encryption key password,has been entered. In some embodiments, the message may be displayed, butthe contents may be obfuscated, such as by blurring or covering textwith black boxes. Other restrictions may prevent any and/or all devicesparticipating in the communication from capturing the contents of themessage, such as by preventing logging and/or disabling screen capturecapabilities. A further refinement may vary a refresh rate associatedwith different portions of a display of the contents such that attemptsto photograph the screen may be blocked or at least allowed to captureonly portions of those contents.

The technical effects of some embodiments of this disclosure may includeestablishing control of access to networks and resources for userdevices when access lists may not be predefined, and reducing and/oreliminating the burden of predefining access lists to control access tonetworks and resources. Moreover, the technical effects of someembodiments may include enhancing network access control by assigningspecific access rights based on access lists to client devicesauthorized to access associated network beacons and resources.

Other technical effects of some embodiments of this disclosure may offergroup management solutions to managing content access and distribution.For example, users of a sales group may have read access to marketingdocuments and presentations, while users in a marketing group may beable to edit and/or annotate the market documents. Similarly, users inan accounting or business services group may be the only ones withaccess to enterprise financial documents. These access controls may beprovided by distributing authorization credentials to devices associatedwith users of the respective group. Each user may then authenticate totheir device, such as by inputting a username, password, authenticationkey, and/or biometric data, before the device may access and/or retrievethe content authorized for distribution to that device. Theseauthentication types are provided as examples only and are not intendedto be limiting as many other types of user authentication are in useand/or may be contemplated in the future.

Content access may be further limited by policies that enforce othercompliance restrictions based on properties of the device such as time,location, device security and/or integrity, presence of another device,software versions, required software, etc. For example, educationalsettings may designate student and instructor groups. These groups maybe further assigned to specific classes such that only student groupmembers associated with a given class may access content associated withthat class. Further, edit access to the content for the class may berestricted to the user(s) in the instructor group and/or student groupmembers may be permitted to add content that only the instructor mayview (e.g., homework assignments.) In some embodiments, the instructorgroup user(s) may be able to push content to student group user(s)and/or activate temporary control of the students' devices to preventthe devices from accessing non-class related content during class time.

To reduce the cost of ownership of user devices and cellular and/or dataservice charges associated with use of such user devices, an enterprisesuch as an educational institution and/or a business may implement a“bring your own device” (BYOD) policy to allow an employee to usehis/her personal device to access enterprise resources rather thanprovide the user with an enterprise owned user device for such purpose.To support such a BYOD policy, a user device administrator (i.e. ITadministrator) may manage a group of personally owned user devices, viaa management application executed by a management server incommunication with the user devices over a network, to provide the userdevices with secure access to enterprise resources.

The user device administrator may enroll user devices into themanagement system to monitor the user devices for securityvulnerabilities and to configure the user devices for secure access toenterprise resources. The user device administrator may create and/orconfigure at least one configuration profile via a user interfaceprovided by the management system. A configuration profile may comprisea set of instructions and/or settings that configure the operationsand/or functions of a user device, which may ensure the security of theaccessed resources. The user device administrator may, for instance,configure an enterprise email configuration profile by specifying thenetwork address and access credentials of an enterprise email accountthat the users of the user devices are authorized to access. Otherconfiguration policies may include, but are not limited to, hardware,software, application, function, cellular, text message, and data userestrictions, which may be based at least in part on the current timeand/or location of the restricted user device. The user deviceadministrator may thereafter deploy the configuration profiles tospecific user devices, such as to groups of user devices of users withsimilar roles, privileges and/or titles.

Access credentials may uniquely identify a client device and/or the userof the client device. For example, the access credentials for a user maycomprise a username, a password, and/or biometric data related to facialrecognition, retina recognition, fingerprint recognition, and the like.Access credentials related to a device may uniquely identify the deviceand may comprise, for example, a unique hardware identifier such as aGUID (Globally Unique Identifier), UUID (Universally Unique Identifier),UDID (Unique Device Identifier), serial number, IMEI (InternationallyMobile Equipment Identity), Wi-Fi MAC (Media Access Control) address,Bluetooth MAC address, a CPU ID, and/or the like, or any combination oftwo or more such hardware identifiers. Additionally, the accesscredentials may be represented by a unique software identifier such atoken or certificate, based at least in part on the aforementionedunique hardware identifiers.

The user devices may also have access to personal configuration profilesthat may be created by the users of the user devices. The user devicesmay, for instance, have access to a personal email configuration profilethat was created by a user of the user device to provide access to herpersonal email account. Thus, a user device enrolled in a BYODmanagement system may have more than one configuration profile for agiven use of the user device, such as a personal email configurationprofile and an enterprise email configuration profile that are both usedfor accessing email accounts on the user device.

The user devices may be instructed to enable and/or disable certainconfiguration profiles according to authorization rights specified bythe user device administrator, such as location and/or time-basedauthorization rights. For example, a BYOD policy may specify that userdevices enrolled in the BYOD management system are authorized forpersonal use outside of the workday and are authorized for business useduring the workday. Similarly, a BYOD device may be restricted toenterprise uses while in work locations and/or prohibited from accessingenterprise resources while outside of secure work locations. Toimplement such a policy, a user device administrator may instruct theuser devices to toggle between personal configuration policies andenterprise configuration policies based on factors such as the currenttime and/or location associated with the user device.

The current time may be based on the current time at the currentlocation of the user device, which may be determined by GPS, Wi-Fi,Cellular Triangulation, etc., or may be based on the current time at aconfigured primary location associated with the user device, which maybe the primary office location of an employee user of the user device.As an example, time-based configuration profile toggling may be providedby instructing a user device to enable business configuration profilesand disable personal configuration profiles while the current time isbetween 9 AM and 5 PM at the current location of the user device, and todisable business configuration profiles and enable personalconfiguration profiles while the current time is between 5 PM and 9 AMat the current location of the user device.

FIG. 1 illustrates a networked environment 100 according to variousembodiments. The networked environment 100 includes a network 110, aclient device 120, a remote server 130, a compliance server 140, and aphysical access point 150. The network 110 includes, for example anytype of wireless network such as a wireless local area network (WLAN), awireless wide area network (WWAN), and/or any other type of wirelessnetwork now known and/or later developed. Additionally, the network 110includes the Internet, intranets, extranets, microwave networks,satellite communications, cellular systems, PCS, infraredcommunications, global area networks, and/or other suitable networks,etc., and/or any combination of two or more such networks. It should beunderstood that embodiments described herein may be used to advantage inany type or combination of wired and/or wireless networks.

In some embodiments, the network 110 facilitates the transport of databetween at least one client device, such as client device 120, theremote server 130, the compliance server 140, and the physical accesspoint 150. Client devices may include a laptop computer, a personaldigital assistant, a cellular telephone, a set-top device, musicplayers, web pads, tablet computer systems, game consoles, and/or otherdevices with like capability. Client device 120 comprises a wirelessnetwork connectivity component, for example, a PCI (Peripheral ComponentInterconnect) card, USB (Universal Serial Bus), PCMCIA (PersonalComputer Memory Card International Association) card, SDIO (SecureDigital Input-Output) card, NewCard, Cardbus, a modem, a wireless radiotransceiver (including an RFID transceiver), near-field communications(NFC) transceiver, and/or the like. Additionally, the client device 120may include a processor for executing applications and/or services, anda memory accessible by the processor to store data and otherinformation. The client device 120 is operable to communicate wirelesslywith the remote server 130 and the physical access point 150 with theaid of the wireless network connectivity component.

Additionally, the client device 120 may store in memory a deviceidentifier 121, user access credentials 122, a device profile 123, andpotentially other data. In some embodiments, the device identifier 121may include a software identifier, a hardware identifier, and/or acombination of software and hardware identifiers. For instance, thedevice identifier 121 may be a unique hardware identifier such as a MACaddress, a CPU ID, and/or other hardware identifiers. The user accesscredentials 122 may include a username, a password, and/or biometricdata related to facial recognition, retina recognition, fingerprintrecognition, and the like. Additionally, the device profile 123 mayinclude a listing of hardware and software attributes that describe theclient device 120. For instance, the device profile 123 may includehardware specifications of the client device 120, version information ofvarious software installed on the client device 120, and/or any otherhardware/software attributes. Additionally, the device profile 123 mayalso include data indicating a date of last virus scan, a date of lastaccess by IT, a date of last tune-up by IT, and/or any other dataindicating a date of last device check.

The client device 120 may further be configured to execute variousapplications such as an “messaging application” 124. The messagingapplication 124 may be executed to exchange real-time communicationswith other client devices. Communication system 125 may be the same ordifferent than the wireless network connectivity component previouslydiscussed, include the same or different communication abilities, andmay at least be specifically able to communicate with physical accesspoints 150, discussed below.

The client device 120 may also be configured to execute otherapplications such as, for example, browser applications, emailapplications, physical access applications, word processingapplications, spreadsheet applications, database applications, and/orother applications. For instance, a browser and/or word processingapplication may be executed in the client device 120, for example, toaccess and render network pages, such as web pages, documents, and/orother network content served up by remote server 130, the complianceserver 140, and/or any other computing system.

The remote server 130 and the compliance server 140 can each beimplemented as, for example, a server computer and/or any other systemcapable of providing computing capability. Further, the remote server130, compliance server 140, and any other system described herein may beconfigured with logic for performing the methods described in thisdisclosure. Although one remote server 130 and one compliance server 140are depicted in FIG. 1, certain embodiments of the networked environment100 include more than one remote server 130 and/or compliance server140. At least one of the servers may be employed and arranged, forexample, in at least one server bank, computer bank, and/or otherarrangements. For example, the server computers together may include acloud computing resource, a grid computing resource, and/or any otherdistributed computing arrangement. Such server computers may be locatedin a single installation and/or may be distributed among many differentgeographical locations. For purposes of convenience, the remote server130 and the compliance server 140 are each referred to herein in thesingular.

Various applications and/or other functionality may be executed in theremote server 130 and the compliance server 140, respectively, accordingto certain embodiments. Also, various data is stored in a data store 131that is part of and/or otherwise accessible to the remote server 130and/or a data store 141 that is part of and/or otherwise accessible tothe compliance server 140. The data stored in each of the data stores131 and 141, for example, may be accessed, modified, removed, and/orotherwise manipulated in association with the operation of theapplications and/or functional entities described herein.

The components executed in the remote server 130 include anauthentication service 135, and may include other applications,services, processes, systems, engines, and/or functionality notdiscussed in detail herein. As used herein, the term “authenticationservice” is meant to generally refer to computer-executable instructionsfor performing the functionality described herein for authorizing andauthenticating client device 120. The authentication service 135 isexecuted to receive a request for access to resources 136 from anapplication executed on client device 120 and to determine whether togrant or deny the request 136. Upon determining to grant the request136, the authentication service 135 may then send access credentials.

The data stored in the data store 131 of the remote server 130 mayinclude, for example, approved device identifiers 132, approved useraccess credentials 133, physical access credentials, resource accesscredentials, and potentially other data. The approved device identifiers132 represents a listing of device identifiers 121 that have beenpre-approved for potential accessing physical access credentials 134which may entitle holders of client devices 120 to access to variousresources. The approved device identifiers 132 may have been previouslyprovided to the remote server 130 by a system administrator and/or thelike. The approved user access credentials 133 represents a listing ofuser access credentials 122 that have been pre-approved for potentialaccessing resource credentials.

The components executed in the compliance server 140 include acompliance service 143, and may include other applications, services,processes, systems, engines, and/or functionality not discussed indetail herein. As used herein, the term “compliance service” is meant togenerally refer to computer-executable instructions for performing thefunctionality described herein for authorizing the devicecharacteristics of another device, such as client device 120. Thecompliance service 143 is executed to determine whether the devicecharacteristics of the client device 120 comply with the compliancerules 142 that are stored in the data store 141. For instance, thecompliance service 143 may identify the device characteristics from thedevice profile 123 of each client device 120. Additionally, thecompliance rules 142 represents a listing of management and securitypolicies, hardware restrictions, software restrictions, and/or mobiledevice management restrictions that may need to be satisfied by theclient device 120 prior to granting the request for resource access 136.

In some embodiments, hardware restrictions included in the compliancerules 142 may comprise restrictions regarding use of specific clientdevices 120 and specific client device features, such as, for instance,cameras, Bluetooth, IRDA, tethering, external storage, a mobile accesspoint, and/or other hardware restrictions. Software restrictionsincluded in the compliance rules 142 may comprise restrictions regardingthe use of specific client device operating systems and/or otherapplications 125, internet browser restrictions, screen capturefunctionality, and/or other software restrictions. Mobile devicemanagement restrictions included in the compliance rules 142 compriseencryption requirements, firmware versions, remote lock and wipefunctionalities, logging and reporting features, GPS tracking, and/orother mobile device management features.

The compliance service 143 may determine whether the devicecharacteristics of a client device 120 satisfy at least one of therestrictions enumerated in the compliance rules 142. For example, thecompliance service 143 may determine that a client device 120 that has acamera, Bluetooth capability, and is executing a specified version of anoperating system is compliant with the compliance rules 142. As anotherexample, the compliance service 143 may determine that a client device120 that is associated with an external storage unit and has screencapture functionality enabled is not compliant with the compliance rules142. All of these restrictions discussed above may affect whether theclient device 120 is entitled to use a given resource(s). In someembodiments, however, the compliance service 143 may not be used andphysical access authorization may be determined solely based on approveduser access credentials 133 and/or approved device identifiers 132.

A user operating a client device 120 may wish to receive at least oneresource(s) so that the user may physical access a building, location,door, gate, drawer, filing cabinet, storage unit, cabinet, etc. In someembodiments, the user may interact with an input device to manipulate anetwork page displayed by a locally executed application, such as abrowser application, to generate the request for resource access 136. Insome embodiments, the user may manipulate a user interface generated bya locally executed application to generate the request 136. In eithercase, the user may provide login information and/or the application mayautomatically retrieve the login information from the memory of theclient device 120. Login information may be, for instance, a unique username, a password, biometric data, and/or other types of user accesscredentials 122. The application may then communicate the request to theenterprise access application 124, which may generate and transmit therequest 136 to the authentication service 135. In some embodiments, theenterprise access application 124 may itself receive the input from theuser directly and then transmit the access request 136 to the remoteserver 130.

Upon receiving the request 136, the authentication service 135determines whether to grant or deny the request 136. In someembodiments, the authentication service 135 may first authenticate theclient device 120 and the user operating the client device 120. To thisend, the authentication service 135 determines whether the deviceidentifier 121 associated with the client device 120 matches one of theidentifiers listed in the listing of approved identifiers 132. Forinstance, the device identifier 121 of the client device 120 may beincluded as part of the request 136 transmitted by the enterprise accessapplication 124. In some embodiments, the authentication service 135 mayrequest the device identifier 121 from the client device 120 in responseto receiving the access request 136. Upon identifying and/or receivingthe device identifier 121, the authentication service 135 determineswhether the device identifier 121 matches one of the approvedidentifiers 132 stored in the data store 131. In some embodiments, theauthentication service 135 may authenticate the client device 120dynamically by determining whether the device identifier 121 is within apredetermined range of approved device identifiers 132. In someembodiments, the authentication service 135 may authenticate the clientdevice 120 dynamically by performing an algorithm on the deviceidentifier 121.

Additionally, the authentication service 135 may also authenticate theuser operating the client device 120 by determining whether the useraccess credentials 122 associated with the user match one of thecredentials in the listing of approved user access credentials 133. Forinstance, the user access credentials 122 associated with the user onthe client device 120 may be included as part of the access request 136transmitted by the enterprise access application 124. In someembodiments, the authentication service 135 may request the user accesscredentials 122 from the client device 120 in response to receiving theaccess request 136. Upon identifying and/or requesting the user accesscredentials 122, the authentication service 135 may determine whetherthe user access credentials 122 matches one of the approved user accesscredentials 133 stored in the data store 131. In some embodiments, theauthentication service 135 may authenticate the user operating theclient device 120 without also authenticating the client device 120. Inother words, certain authenticated users may be authorized to gain therequested physical access regardless of what device they used to submitthe resource request 136.

In some embodiments, having authenticated the client device 120 and theuser operating the client device 120 as authorized to receive theresource(s), the authentication service 135 communicates with thecompliance service 143 to further authorize the client device 120 toreceive the resource(s). In some embodiments, the compliance service 143authorizes the client device 120 by determining whether devicecharacteristics of the client device 120 comply with applicablecompliance rules 142. For instance, the compliance service 143 mayidentify the device characteristics of the client device 120 from thedevice profile 123. All or part of the device profile 123 may have beenprovided by the client device 120 in conjunction with the request 136and/or may be subsequently requested from the client device 120 by theauthentication service 135 and/or the compliance service 143. Thecompliance service 143 then analyzes the device characteristics todetermine whether the software restrictions, hardware restrictions,and/or device management restrictions defined in the compliance rules142 are satisfied and returns the result of the determination to theauthentication service 135. In an alternative embodiment, theauthentication service 135 may include and perform functionality fordetermining whether the client device 120 complies with the compliancerules 143.

If the authentication service 135 determines and/or receives adetermination that the client device 120 is authorized, theauthentication service 135 then associates the client device 120 with atleast one resource(s). In some embodiments, the authentication service135 sends the physical access credentials 134 to the client device 120and authorizes the client device 120 to use such credentials inconnection with accessing physical access points 150. In someembodiments, the authentication service 135 may also send the physicalaccess credentials to physical access point 150.

In some embodiments, the resource(s) may be revoked at any time by theremote server 130. Revocation may occur for any number of reasons,including but not limited to, a change in device profile 123, a changein approved device identifiers 132, a change in approved user accesscredentials 133, expiration of a defined time period, and/or a requestfrom the user of the client device 120.

In some embodiments, the physical access point 150 is anelectro-mechanical device capable of sending and/or receivinginformation, and in response thereto opening a physical barrier, forexample a building, location, door, gate, drawer, filing cabinet,storage unit, cabinet, etc. Depending on the embodiment, the physicalaccess point may or may not be in communication with network 110 andservers and devices connected therewith. In these embodiments, thephysical access point may have authorized physical access credentials134 embedded and/or stored therein, either in a ROM-type storage unit,and/or in a non-networked RAM-type storage unit. A non-networkedRAM-type storage unit could be updated locally by direct connection viaUSB and/or the like, with additional security mechanisms to preventunwanted tampering/changing of the embedded/stored physical accesscredentials 134.

The physical access point 150 may include a data store 151 formaintaining data and/or applications which relate to determining whethera client device 120 may be allowed access by the physical access point150. In some embodiments, the data store 151 may only include a singleaccess code and/or datum that is expected to be matched by any clientdevice 120 providing the same, thereby entitling the client device 120to access beyond the physical barrier. In some embodiments, the datastore 151 may include a plurality of access codes, any of which may bematched by a client device 120 to verify authority to access beyond thephysical barrier. The physical access point may have a processor toimplement such methods.

The physical access point 150 may also include a physical lock actuator152, for example, a solenoid and/or other electro-mechanical actuator,which is operable to physically unlock the physical barrier upon commandto do so by the physical access point 150. The physical access point mayalso include a communication system 153 for sending and receivinginformation with a client device 120 (for example, an RFID transceiver,a wireless radio transceiver, a near field communication device, and/orthe like).

FIG. 2 is a flow chart setting forth the general stages involved in amethod 300 consistent with embodiments of this disclosure for providingapplication specific certificate deployment. Method 200 may beimplemented using elements of operating environment 100 as describedabove, a schematic block diagram 400 and a virtual desktopinfrastructure (VDI) system 500, as described below. Method 200 isdescribed below with respect to operations performed by a computingdevice, with the understanding that such a computing device may compriseany number devices programmed for operation of any and/or all of thesteps of method 200. The described computing device may comprise, forexample, client device 120, remote server 130, compliance server 140,and/or physical access point 150. Ways to implement the stages of method200 will be described in greater detail below.

Method 200 may begin at stage 205 where a computing device may requestaccess to a particular resource. For example, an application may attemptto retrieve a plurality of data, such as documents, web pages, emails,etc. and/or may attempt to execute commands on a remote system such asupdating a database, copying or modifying remote files, performingremote procedure calls, etc.

Method 200 may then advance to stage 210 where the computing device maydetermine whether the resource(s) require a secure retrieval. Forexample, unencrypted access to the resource(s) may be prohibited.

If no secure retrieval is required, method 200 may then advance to stage215 where the computing device may simply retrieve and/or access therequested resource(s). Otherwise, method 200 may advance to stage 230where the computing device may generate a security certificate accordingto a public key cryptography algorithm. Such a certificate normallycomprises a public key and a private key as well as a unique issueridentifier. The certificate may be generated by the applicationrequesting the secured resource(s), by another application, and/or bythe operating system executing on the mobile device. In someembodiments, the certificate may be generated by another device, such asby remote server 130.

Public-key cryptography, also known as asymmetric cryptography, is aclass of cryptographic algorithms which require two separate keys, oneof which is secret (or private) and one of which is public. Althoughdifferent, the two parts of this key pair are mathematically linked. Thepublic key may be used to encrypt data and/or to verify a digitalsignature; whereas the private key is used to decrypt ciphertext or tocreate a digital signature.

Public-key algorithms are based on mathematical problems which currentlyadmit no efficient solution that are inherent in certain integerfactorization, discrete logarithm, and elliptic curve relationships. Itis computationally easy for a user to generate their own public andprivate key-pair and to use them for encryption and decryption. Thestrength lies in the fact that it is “impossible” (computationallyunfeasible) for a properly generated private key to be determined fromits corresponding public key.

Public-key algorithms are fundamental security ingredients incryptosystems, applications and protocols. They underpin such Internetstandards as Transport Layer Security (TLS), PGP, and GPG. Some publickey algorithms provide key distribution and secrecy (e.g.,Diffie-Hellman key exchange), some provide digital signatures (e.g.,Digital Signature Algorithm), and some provide both (e.g., RSA).

A public key infrastructure (PKI) is a set of hardware, software,people, policies, and procedures needed to create, manage, distribute,use, store, and revoke digital certificates. In cryptography, a PKI isan arrangement that binds public keys with respective user identities bymeans of a certificate authority (CA). The user identity must be uniquewithin each CA domain. The third-party validation authority (VA) canprovide this information on behalf of CA. The binding is establishedthrough the registration and issuance process, which, depending on theassurance level of the binding, may be carried out by software at a CAor under human supervision. The PKI role that assures this binding iscalled the registration authority (RA), which ensures that the publickey is bound to the individual to which it is assigned in a way thatensures non-repudiation.

After generating the certificate at stage 230, method 200 may advance tostage 235 where the computing device may upload the public key portionof the security certificate. For example, the public key may be placedin a shared memory portion, such as an application configurationchannel, that may be used to communicate data across a network. Thismemory portion may be shared among multiple applications and/or may bededicated and accessible only to a specific application. Anothercomputing device, such as remote server 130, may retrieve the public keyfrom the shared memory portion and/or may receive the public key as atransmission. The public key may then be verified and signed by acertificate authority. In some embodiments, the computing device, suchas client device 120, associated with the public key may need to beverified to be in compliance with compliance rules 142 before the keymay be signed.

Method 200 may then advance to stage 240 where the computing device mayreceive the signed public key. For example, a certificate authority maytransmit the signed public key to client device 120. An operating systemexecuting on client device 120 may place the signed public key in amemory segment accessible to the requesting application. In someembodiments, this memory segment may also be accessible to a pluralityof other applications.

Method 200 may then advance to stage 245 where the computing device mayretrieve the requested resource(s). For example, client device 120 maytransmit a request to retrieve the resource(s) from remote server 130.Remote server 130 may encrypt the resource(s) according to the publickey and transmit the encrypted resource(s) back to client device 120.

Method 200 may then advance to stage 250 where the computing device maydecrypt and utilize the resource(s). For example, client device 120 maydecrypt the encrypted resource(s) using the private key corresponding tothe public key used during the encryption. The resource(s) may then bemade available to the application for display, data processing and/ormanipulation. Method 200 may then end.

In some embodiments, the security certificate may be shared among aplurality of applications, such as by placing the private key in amemory segment accessible only to a restricted list of applications.These applications may then request resources from remote server 130 andindicate a unique identifier of the signed security certificate in orderto have the resources encrypted using the established public key. Insome other embodiments, a new security certificate may be generated foreach resource request.

FIG. 3 is a block diagram of a communication system 300 providingapplication specific certificate deployment. Communication system 300may comprise client device 120, remote server 130, and a certificateauthority 305. In cryptography, a certificate authority (CA) is anentity that issues digital certificates. The digital certificatecertifies the ownership of a public key by the named subject of thecertificate. This allows others (relying parties) to rely uponsignatures or assertions made by the private key that corresponds to thepublic key that is certified. In this model of trust relationships, a CAis a trusted third party that is trusted by both the subject (owner) ofthe certificate and the party relying upon the certificate. CAs arecharacteristic of many public key infrastructure (PKI) schemes.

In some embodiments, a public key associated with a security certificatemay be stored in a shared memory segment 310 associated with clientdevice 120. The public key may be uploaded to remote server 130 vianetwork 110, which may validate the compliance of client device 120 withany applicable security and/or management requirements. The key may thenbe sent to certificate authority 305 for verification and signing beforebeing returned to client device 120. In some embodiments, client device120 may communicate directly with certificate authority 305 withoutrelaying the unsigned public key through remote server 130.

FIG. 4 illustrates schematic block diagram 400 of the remote server 130and the client device 140 according to embodiments of the presentdisclosure. The remote server 130 includes at least one processorcircuit, for example, having a processor 403 and a memory 406, both ofwhich are coupled to a local interface 409. To this end, the remoteserver 130 may comprise, for example, at least one server computerand/or like device. Similarly, the client device 140 includes at leastone processor circuit, for example, having a processor 413 and a memory416, both of which are coupled to a local interface 419. Additionally,the client device 120 may be in data communication with a display forrendering user interfaces and at least one other I/O device forinputting and outputting data. To this end, the client device 140 maycomprise, for example, at least one mobile wireless device, computer,and/or like device. The local interfaces 409 and 419 may comprise, forexample, a data bus with an accompanying address/control bus and/orother bus structure as can be appreciated.

Stored in the memories 406 and 416 are both data and several componentsthat are executable by the processors 403 and 413. In particular, storedin the memory 406/416 and executable by the processors 403 and 413 are aauthentication service 135, an enterprise access application 124, andpotentially other applications. Also stored in the memories 406 and 416may be a data stores 131 and 418 and other data. In addition, anoperating system may be stored in the memories 406 and 416 andexecutable by the processors 403 and 413.

It is to be understood that there may be other applications that arestored in the memories 406 and 416 and are executable by the processors403 and 413 as can be appreciated. Where any component discussed hereinis implemented in the form of software, any one of a number ofprogramming languages may be employed such as, for example, C, C++, C#,Objective C, Java, JavaScript, Perl, PHP, Visual Basic, Python, Ruby,Delphi, Flash, and/or other programming languages.

A number of software components are stored in the memories 406 and 416and are executable by the processors 403 and 413. In this respect, theterm “executable” means a program file that is in a form that canultimately be run by the processors 403 and 413. Examples of executableprograms may be, for example, a compiled program that can be translatedinto machine code in a format that can be loaded into a random accessportion of the memories 406 and 416 and run by the processors 403 and413, source code that may be expressed in proper format such as objectcode that is capable of being loaded into a random access portion of thememory 406/416 and executed by the processors 403 and 413, and/or sourcecode that may be interpreted by another executable program to generateinstructions in a random access portion of the memories 406 and 416 tobe executed by the processors 403 and 413, etc. An executable programmay be stored in any portion and/or component of the memories 406 and416 including, for example, random access memory (RAM), read-only memory(ROM), hard drive, solid-state drive, USB flash drive, memory card,optical disc such as compact disc (CD) and/or digital versatile disc(DVD), floppy disk, magnetic tape, and/or other memory components.

The memories 406 and 416 is defined herein as including both volatileand nonvolatile memory and data storage components. Volatile componentsare those that do not retain data values upon loss of power. Nonvolatilecomponents are those that retain data upon a loss of power. Thus, thememories 406 and 416 may comprise, for example, random access memory(RAM), read-only memory (ROM), hard disk drives, solid-state drives, USBflash drives, memory cards accessed via a memory card reader, floppydisks accessed via an associated floppy disk drive, optical discsaccessed via an optical disc drive, magnetic tapes accessed via anappropriate tape drive, and/or other memory components, and/or acombination of any two and/or more of these memory components. Inaddition, the RAM may comprise, for example, static random access memory(SRAM), dynamic random access memory (DRAM), and/or magnetic randomaccess memory (MRAM) and other such devices. The ROM may comprise, forexample, a programmable read-only memory (PROM), an erasableprogrammable read-only memory (EPROM), an electrically erasableprogrammable read-only memory (EEPROM), and/or other like memory device.

Also, the processors 403 and 413 may represent multiple processors, andthe memories 406 and 416 may represent multiple memories that operate inparallel processing circuits, respectively. In such a case, the localinterfaces 409 and 419 may be an appropriate network 109 (FIG. 1) thatfacilitates communication between any two of the multiple processors 403and 413, and/or between any two of the memories 406 and 416, etc. Thelocal interfaces 409 and 419 may comprise additional systems designed tocoordinate this communication, including, for example, performing loadbalancing. The processors 403 and 413 may be of electrical and/or ofsome other available construction.

Although the authentication service 135, the enterprise applicationservice 124, and other various systems described herein may be embodiedin software and/or code executed by general purpose hardware asdiscussed above, as an alternative the same may also be embodied indedicated hardware and/or a combination of software/general purposehardware and dedicated hardware. If embodied in dedicated hardware, eachcan be implemented as a circuit and/or state machine that employs anyone of and/or a combination of a number of technologies. Thesetechnologies may include, but are not limited to, discrete logiccircuits having logic gates for implementing various logic functionsupon an application of at least one data signal, application specificintegrated circuits having appropriate logic gates, and/or othercomponents, etc.

FIG. 5 illustrates components of a virtual desktop infrastructure (VDI)system 500 in which embodiments of the present disclosure may beimplemented. In VDI system 500, VDI client software programs such as VDIclient 510, run on operating systems of local computing devices, e.g.,client machine 508 on top of an operating system (OS) 511. VDI clientsprovides an interface for the users to access their desktops, which maybe running in one of virtual machines 557 or blade server (not shown) ina data center that is remote from the users' locations. The term“desktop” may refer to the instance of an interactive operatingenvironment provided by a computer operating system and softwareapplications, typically in the form of a display and sound output andkeyboard and mouse input. With VDI clients, users can access desktopsrunning in a remote data center through network 110, from any location,using a general purpose computer running a commodity operating systemand a VDI client software program such as VMware® View, or a specialpurpose thin client such as those available from Dell, HP, NEC, SunMicrosystems, Wyse, and others.

VDI system 500 may include a domain controller 535, such as Microsoft®Active Directory® that manages user accounts 536 including user log-ininformation, and a connection broker 537 that manages connectionsbetween VDI clients and desktops running in virtual machines 557 orother platforms. Domain controller 535 and connection broker 537 may runon separate servers or in separate virtual machines running on the sameserver or different servers. In the embodiments of the presentdisclosure illustrated herein, desktops are running in virtual machines557 are instantiated on a plurality of physical computers 550, 552, 554,each of which includes virtualization software 558 and hardware 559.Physical computes 550, 552, 554 may be controlled by a virtual machinemanagement server 540, and be coupled to a shared persistent storagesystem 560.

All of the components of VDI system 500 communicate via network 110. Forsimplicity, a single network is shown but it should be recognized that,in actual implementations, the components of VDI system 500 may beconnected over the same network or different networks. Furthermore, aparticular configuration of the virtualized desktop infrastructure isdescribed above and illustrated in FIG. 5, but it should be recognizedthat one or more embodiments of the present disclosure may be practicedwith other configurations of the virtualized desktop infrastructure.

The embodiments and functionalities described herein may operate via amultitude of computing systems, including wired and wireless computingsystems, mobile computing systems (e.g., mobile telephones, tablet orslate type computers, laptop computers, etc.). In addition, theembodiments and functionalities described herein may operate overdistributed systems, where application functionality, memory, datastorage and retrieval and various processing functions may be operatedremotely from each other over a distributed computing network, such asthe Internet or an intranet. User interfaces and information of varioustypes may be displayed via on-board computing device displays or viaremote display units associated with one or more computing devices. Forexample user interfaces and information of various types may bedisplayed and interacted with on a wall surface onto which userinterfaces and information of various types are projected. Interactionwith the multitude of computing systems with which embodiments of thisdisclosure may be practiced include, keystroke entry, touch screenentry, voice or other audio entry, gesture entry where an associatedcomputing device is equipped with detection (e.g., camera) functionalityfor capturing and interpreting user gestures for controlling thefunctionality of the computing device, and the like. The Figures aboveand their associated descriptions provide a discussion of a variety ofoperating environments in which embodiments of this disclosure may bepracticed. However, the devices and systems illustrated and discussedwith respect to the Figures are for purposes of example and illustrationand are not limiting of a vast number of computing device configurationsthat may be utilized for practicing embodiments of this disclosure asdescribed herein.

The term computer readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Systemmemory, removable storage, and non-removable storage are all computerstorage media examples (i.e., memory storage.) Computer storage mediamay include, but is not limited to, RAM, ROM, electrically erasableread-only memory (EEPROM), flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store.

The term computer readable media as used herein may also includecommunication media. Communication media may be embodied by computerreadable instructions, data structures, program modules, non-transitorymedia, and/or other data in a modulated data signal, such as a carrierwave or other transport mechanism, and includes any information deliverymedia. The term “modulated data signal” may describe a signal that hasone or more characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, radiofrequency (RF), infrared, and other wireless media.

A number of applications and data files may be used to perform processesand/or methods as described above. The aforementioned processes areexamples, and a processing unit may perform other processes. Otherprogramming modules that may be used in accordance with embodiments ofthis disclosure may include electronic mail, calendar, and contactsapplications, data processing applications, word processingapplications, spreadsheet applications, database applications, slidepresentation applications, drawing or computer-aided applicationprograms, etc.

Generally, consistent with embodiments of this disclosure, programmodules may include routines, programs, components, data structures, andother types of structures that may perform particular tasks or that mayimplement particular abstract data types. Moreover, embodiments of thedisclosure may be practiced with other computer system configurations,including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like. Embodiments of thisdisclosure may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

Furthermore, embodiments of this disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. Embodiments of this disclosure may also be practicedusing other technologies capable of performing logical operations suchas, for example, AND, OR, and NOT, including but not limited tomechanical, optical, fluidic, and quantum technologies. In addition,embodiments of the disclosure may be practiced within a general purposecomputer or in any other circuits or systems.

Embodiments of this disclosure may, for example, be implemented as acomputer process and/or method, a computing system, an apparatus,device, or appliance, and/or as an article of manufacture, such as acomputer program product or computer readable media. The computerprogram product may be a computer storage media readable by a computersystem and encoding a computer program of instructions for executing acomputer process. The computer program product may also be a propagatedsignal on a carrier readable by a computing system and encoding acomputer program of instructions for executing a computer process.Accordingly, the present disclosure may be embodied in hardware and/orin software (including firmware, resident software, micro-code, etc.).In other words, embodiments of the present disclosure may take the formof a computer program product on a computer-usable or computer-readablestorage medium having computer-usable or computer-readable program codeembodied in the medium for use by or in connection with an instructionexecution system. A computer-usable or computer-readable medium may beany medium that can contain, store, communicate, propagate, or transportthe program for use by or in connection with the instruction executionsystem, apparatus, or device.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific computer-readable medium examples (anon-exhaustive list), the computer-readable medium may include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a portable compact disc read-only memory(CD-ROM). Note that the computer-usable or computer-readable mediumcould even be paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

Embodiments of this disclosure may be practiced via a system-on-a-chip(SOC) where each and/or many of the elements described above may beintegrated onto a single integrated circuit. Such an SOC device mayinclude one or more processing units, graphics units, communicationsunits, system virtualization units and various applicationfunctionalities, all of which may be integrated (or “burned”) onto thechip substrate as a single integrated circuit. When operating via anSOC, the functionality, described herein, with respect to trainingand/or interacting with any element may operate via application-specificlogic integrated with other components of the computing device/system onthe single integrated circuit (chip).

Embodiments of this disclosure are described above with reference toblock diagrams and/or operational illustrations of methods, systems, andcomputer program products according to embodiments of the disclosure.The functions/acts noted in the blocks may occur out of the order asshown in any flowchart. For example, two blocks shown in succession mayin fact be executed substantially concurrently or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality/acts involved.

While certain embodiments have been described, other embodiments mayexist. Furthermore, although embodiments of the present disclosure havebeen described as being associated with data stored in memory and otherstorage mediums, data can also be stored on or read from other types ofcomputer-readable media, such as secondary storage devices, like harddisks, floppy disks, or a CD-ROM, a carrier wave from the Internet, orother forms of RAM or ROM. Further, the disclosed methods' stages may bemodified in any manner, including by reordering stages and/or insertingor deleting stages, without departing from the disclosure.

Embodiments of the present disclosure, for example, are described abovewith reference to block diagrams and/or operational illustrations ofmethods, systems, and computer program products according to embodimentsof the disclosure. The functions/acts noted in the blocks may occur outof the order as shown in any flowchart. For example, two blocks shown insuccession may in fact be executed substantially concurrently or theblocks may sometimes be executed in the reverse order, depending uponthe functionality/acts involved.

While certain embodiments of the disclosure have been described, otherembodiments may exist. Furthermore, although embodiments of the presentdisclosure have been described as being associated with data stored inmemory and other storage mediums, data can also be stored on or readfrom other types of computer-readable media, such as secondary storagedevices, like hard disks, floppy disks, or a CD-ROM, a carrier wave fromthe Internet, or other forms of RAM or ROM. Further, the disclosedmethods' stages may be modified in any manner, including by reorderingstages and/or inserting or deleting stages, without departing from thedisclosure.

All rights including copyrights in the code included herein are vestedin and the property of the Assignee. The Assignee retains and reservesall rights in the code included herein, and grants permission toreproduce the material only in connection with reproduction of thegranted patent and for no other purpose.

While the specification includes examples, the disclosure's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments of the disclosure.

What is claimed is:
 1. A method comprising: transmitting a request togenerate a security certificate; determining whether the securitycertificate has been generated; and in response to determining that thesecurity certificate has been generated: retrieving the securitycertificate, authenticating the security certificate, deploying theauthenticated security certificate, encrypting a plurality of resourcesaccording to the authenticated security certificate, and transmittingthe encrypted plurality of resources to at least one recipient of thedeployed authenticated security certificate.
 2. The method of claim 1,wherein determining whether the security certificate has been generatedcomprises determining whether the security certificate has been storedin a memory cache.
 3. The method of claim
 2. wherein the securitycertificate stored in the memory cache comprises a public keycertificate.
 4. The method of claim 2, wherein the memory cache isassociated with an application.
 5. The method of claim 4, wherein thememory cache comprises a secure memory cache accessible only by theapplication.
 6. The method of claim 4, wherein the memory cachecomprises an insecure memory cache accessible by a plurality ofapplications.
 7. The method of claim 6, further comprising: providing asecond public key certificate to the application; and retrieving aprivate key certificate from the memory cache, wherein the private keycertificate is encrypted according to the second public key certificate.8. The method of claim 4, wherein deploying the authenticated securitycertificate comprises providing the authenticated security certificateto the application.
 9. The method of claim 1, wherein the request togenerate the security certificate is transmitted in response toreceiving a request to access at least one resource.
 10. An apparatuscomprising: a memory store; and a processor coupled to the memory store,wherein the processor is configured to: generate a security certificatecomprising a public key and a private key, store the public key in ashared segment of the memory store, retrieve a signed version of thepublic key from the shared segment of the memory store, retrieve aplurality of resources encrypted according to the public key, anddecrypt the plurality of encrypted resources according to the privatekey.
 11. The apparatus of claim 10, wherein the processor is configuredto generate the security certificate in response to a notification thata request to retrieve the plurality of resources cannot be completed.12. The apparatus of claim 11, wherein the request to retrieve theplurality of resources cannot be completed because the plurality ofresources comprises a plurality of secure resources.
 13. The apparatusof claim 12, wherein the plurality of encrypted resources comprises acompleted delivery of the requested plurality of resources.
 14. Theapparatus of claim 10, wherein the security certificate comprises aone-time use security certificate.
 15. The apparatus of claim 10,wherein the processor is further configured to store the second privatekey for re-use.
 16. The apparatus of claim 15, wherein the processor isfurther configured to: re-encrypt the second private key; and store thesecond private key in the shared segment of the memory store.
 17. Anon-transitory computer readable medium comprising program code that,when executed, performs a method comprising: generating a securitycertificate comprising a public key and a first private key, storing thepublic key in a shared segment of a memory store, retrieving a secondprivate key from the shared segment of the memory store, wherein thesecond private key is encrypted according to the public key, decryptingthe second private key according to the first private key, retrieving aplurality of encrypted data, and decrypting the plurality of encrypteddata according to the decrypted second private key.
 18. Thenon-transitory computer readable medium of claim 17, wherein the methodfurther comprises storing the second private key in a second segment ofthe memory store, wherein the second segment of the memory storecomprises a restricted access segment of the memory store.
 19. Thenon-transitory computer readable medium of claim 18, wherein access tothe restricted access segment of the memory store is limited to aplurality of managed applications.
 20. The non-transitory computerreadable medium of claim 18, wherein the plurality of managedapplications each have access to the security certificate.